Autogenerated HTML docs for v2.33.0-69-gc4203
diff --git a/RelNotes/2.34.0.txt b/RelNotes/2.34.0.txt new file mode 100644 index 0000000..cfbea48 --- /dev/null +++ b/RelNotes/2.34.0.txt
@@ -0,0 +1,48 @@ +Git 2.34 Release Notes +====================== + +Updates since Git 2.33 +---------------------- + +UI, Workflows & Features + + * Pathname expansion (like "~username/") learned a way to specify a + location relative to Git installation (e.g. its $sharedir which is + $(prefix)/share), with "%(prefix)". + + +Performance, Internal Implementation, Development Support etc. + + * "git bisect" spawned "git show-branch" only to pretty-print the + title of the commit after checking out the next version to be + tested; this has been rewritten in C. + + * "git add" can work better with the sparse index. + + * Support for ancient versions of cURL library (pre 7.19.4) has been + dropped. + + * A handful of tests that assumed implementation details of files + backend for refs have been cleaned up. + + * trace2 logs learned to show parent process name to see in what + context Git was invoked. + + * Loading of ref tips to prepare for common ancestry negotiation in + "git fetch-pack" has been optimized by taking advantage of the + commit graph when available. + + +Fixes since v2.33 +----------------- + + * Input validation of "git pack-objects --stdin-packs" has been + corrected. + (merge 561fa03529 ab/pack-stdin-packs-fix later to maint). + + * Bugfix for common ancestor negotiation recently introduced in "git + push" code path. + (merge 82823118b9 jt/push-negotiation-fixes later to maint). + + * Other code cleanup, docfix, build fix, etc. + (merge 1d9c8daef8 ab/bundle-doc later to maint).
diff --git a/config.txt b/config.txt index bf82766..0c0e6b8 100644 --- a/config.txt +++ b/config.txt
@@ -298,6 +298,15 @@ tilde expansion happens to such a string: `~/` is expanded to the value of `$HOME`, and `~user/` to the specified user's home directory. ++ +If a path starts with `%(prefix)/`, the remainder is interpreted as a +path relative to Git's "runtime prefix", i.e. relative to the location +where Git itself was installed. For example, `%(prefix)/bin/` refers to +the directory in which the Git executable itself lives. If Git was +compiled without runtime prefix support, the compiled-in prefix will be +subsituted instead. In the unlikely event that a literal path needs to +be specified that should _not_ be expanded, it needs to be prefixed by +`./`, like so: `./%(prefix)/bin`. Variables
diff --git a/git-bundle.html b/git-bundle.html index a933375..cca390e 100644 --- a/git-bundle.html +++ b/git-bundle.html
@@ -761,19 +761,42 @@ <div class="sect1"> <h2 id="_description">DESCRIPTION</h2> <div class="sectionbody"> -<div class="paragraph"><p>Some workflows require that one or more branches of development on one -machine be replicated on another machine, but the two machines cannot -be directly connected, and therefore the interactive Git protocols (git, -ssh, http) cannot be used.</p></div> -<div class="paragraph"><p>The <em>git bundle</em> command packages objects and references in an archive -at the originating machine, which can then be imported into another -repository using <em>git fetch</em>, <em>git pull</em>, or <em>git clone</em>, -after moving the archive by some means (e.g., by sneakernet).</p></div> -<div class="paragraph"><p>As no -direct connection between the repositories exists, the user must specify a -basis for the bundle that is held by the destination repository: the -bundle assumes that all objects in the basis are already in the -destination repository.</p></div> +<div class="paragraph"><p>Create, unpack, and manipulate "bundle" files. Bundles are used for +the "offline" transfer of Git objects without an active "server" +sitting on the other side of the network connection.</p></div> +<div class="paragraph"><p>They can be used to create both incremental and full backups of a +repository, and to relay the state of the references in one repository +to another.</p></div> +<div class="paragraph"><p>Git commands that fetch or otherwise "read" via protocols such as +<code>ssh://</code> and <code>https://</code> can also operate on bundle files. It is +possible <a href="git-clone.html">git-clone(1)</a> a new repository from a bundle, to use +<a href="git-fetch.html">git-fetch(1)</a> to fetch from one, and to list the references +contained within it with <a href="git-ls-remote.html">git-ls-remote(1)</a>. There’s no +corresponding "write" support, i.e.a <em>git push</em> into a bundle is not +supported.</p></div> +<div class="paragraph"><p>See the "EXAMPLES" section below for examples of how to use bundles.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_bundle_format">BUNDLE FORMAT</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Bundles are <code>.pack</code> files (see <a href="git-pack-objects.html">git-pack-objects(1)</a>) with a +header indicating what references are contained within the bundle.</p></div> +<div class="paragraph"><p>Like the the packed archive format itself bundles can either be +self-contained, or be created using exclusions. +See the "OBJECT PREREQUISITES" section below.</p></div> +<div class="paragraph"><p>Bundles created using revision exclusions are "thin packs" created +using the <code>--thin</code> option to <a href="git-pack-objects.html">git-pack-objects(1)</a>, and +unbundled using the <code>--fix-thin</code> option to <a href="git-index-pack.html">git-index-pack(1)</a>.</p></div> +<div class="paragraph"><p>There is no option to create a "thick pack" when using revision +exclusions, users should not be concerned about the difference. By +using "thin packs" bundles created using exclusions are smaller in +size. That they’re "thin" under the hood is merely noted here as a +curiosity, and as a reference to other documentation</p></div> +<div class="paragraph"><p>See <a href="technical/bundle-format.html">the <code>bundle-format</code> +documentation</a> for more details and the discussion of "thin pack" in +<a href="technical/pack-format.html">the pack format documentation</a> for +further details.</p></div> </div> </div> <div class="sect1"> @@ -919,25 +942,77 @@ <div class="sect1"> <h2 id="_specifying_references">SPECIFYING REFERENCES</h2> <div class="sectionbody"> -<div class="paragraph"><p><em>git bundle</em> will only package references that are shown by -<em>git show-ref</em>: this includes heads, tags, and remote heads. References -such as <code>master~1</code> cannot be packaged, but are perfectly suitable for -defining the basis. More than one reference may be packaged, and more -than one basis can be specified. The objects packaged are those not -contained in the union of the given bases. Each basis can be -specified explicitly (e.g. <code>^master~10</code>), or implicitly (e.g. -<code>master~10..master</code>, <code>--since=10.days.ago master</code>).</p></div> -<div class="paragraph"><p>It is very important that the basis used be held by the destination. -It is okay to err on the side of caution, causing the bundle file +<div class="paragraph"><p>Revisions must accompanied by reference names to be packaged in a +bundle.</p></div> +<div class="paragraph"><p>More than one reference may be packaged, and more than one set of prerequisite objects can +be specified. The objects packaged are those not contained in the +union of the prerequisites.</p></div> +<div class="paragraph"><p>The <em>git bundle create</em> command resolves the reference names for you +using the same rules as <code>git rev-parse --abbrev-ref=loose</code>. Each +prerequisite can be specified explicitly (e.g. <code>^master~10</code>), or implicitly +(e.g. <code>master~10..master</code>, <code>--since=10.days.ago master</code>).</p></div> +<div class="paragraph"><p>All of these simple cases are OK (assuming we have a "master" and +"next" branch):</p></div> +<div class="listingblock"> +<div class="content"> +<pre><code>$ git bundle create master.bundle master +$ echo master | git bundle create master.bundle --stdin +$ git bundle create master-and-next.bundle master next +$ (echo master; echo next) | git bundle create master-and-next.bundle --stdin</code></pre> +</div></div> +<div class="paragraph"><p>And so are these (and the same but omitted <code>--stdin</code> examples):</p></div> +<div class="listingblock"> +<div class="content"> +<pre><code>$ git bundle create recent-master.bundle master~10..master +$ git bundle create recent-updates.bundle master~10..master next~5..next</code></pre> +</div></div> +<div class="paragraph"><p>A revision name or a range whose right-hand-side cannot be resolved to +a reference is not accepted:</p></div> +<div class="listingblock"> +<div class="content"> +<pre><code>$ git bundle create HEAD.bundle $(git rev-parse HEAD) +fatal: Refusing to create empty bundle. +$ git bundle create master-yesterday.bundle master~10..master~5 +fatal: Refusing to create empty bundle.</code></pre> +</div></div> +</div> +</div> +<div class="sect1"> +<h2 id="_object_prerequisites">OBJECT PREREQUISITES</h2> +<div class="sectionbody"> +<div class="paragraph"><p>When creating bundles it is possible to create a self-contained bundle +that can be unbundled in a repository with no common history, as well +as providing negative revisions to exclude objects needed in the +earlier parts of the history.</p></div> +<div class="paragraph"><p>Feeding a revision such as <code>new</code> to <code>git bundle create</code> will create a +bundle file that contains all the objects reachable from the revision +<code>new</code>. That bundle can be unbundled in any repository to obtain a full +history that leads to the revision <code>new</code>:</p></div> +<div class="listingblock"> +<div class="content"> +<pre><code>$ git bundle create full.bundle new</code></pre> +</div></div> +<div class="paragraph"><p>A revision range such as <code>old..new</code> will produce a bundle file that +will require the revision <code>old</code> (and any objects reachable from it) +to exist for the bundle to be "unbundle"-able:</p></div> +<div class="listingblock"> +<div class="content"> +<pre><code>$ git bundle create full.bundle old..new</code></pre> +</div></div> +<div class="paragraph"><p>A self-contained bundle without any prerequisites can be extracted +into anywhere, even into an empty repository, or be cloned from +(i.e., <code>new</code>, but not <code>old..new</code>).</p></div> +<div class="paragraph"><p>It is okay to err on the side of caution, causing the bundle file to contain objects already in the destination, as these are ignored when unpacking at the destination.</p></div> -<div class="paragraph"><p><code>git clone</code> can use any bundle created without negative refspecs -(e.g., <code>new</code>, but not <code>old..new</code>). -If you want to match <code>git clone --mirror</code>, which would include your +<div class="paragraph"><p>If you want to match <code>git clone --mirror</code>, which would include your refs such as <code>refs/remotes/*</code>, use <code>--all</code>. If you want to provide the same set of refs that a clone directly from the source repository would get, use <code>--branches --tags</code> for the <code><git-rev-list-args></code>.</p></div> +<div class="paragraph"><p>The <em>git bundle verify</em> command can be used to check whether your +recipient repository has the required prerequisite commits for a +bundle.</p></div> </div> </div> <div class="sect1"> @@ -949,7 +1024,7 @@ but we can move data from A to B via some mechanism (CD, email, etc.). We want to update R2 with development made on the branch master in R1.</p></div> <div class="paragraph"><p>To bootstrap the process, you can first create a bundle that does not have -any basis. You can use a tag to remember up to what commit you last +any prerequisites. You can use a tag to remember up to what commit you last processed, in order to make it easy to later update the other repository with an incremental bundle:</p></div> <div class="listingblock"> @@ -994,7 +1069,7 @@ </div></div> <div class="paragraph"><p>If you know up to what commit the intended recipient repository should have the necessary objects, you can use that knowledge to specify the -basis, giving a cut-off point to limit the revisions and objects that go +prerequisites, giving a cut-off point to limit the revisions and objects that go in the resulting bundle. The previous example used the lastR2bundle tag for this purpose, but you can use any other options that you would give to the <a href="git-log.html">git-log(1)</a> command. Here are more examples:</p></div> @@ -1003,7 +1078,7 @@ <div class="content"> <pre><code>$ git bundle create mybundle v1.0.0..master</code></pre> </div></div> -<div class="paragraph"><p>You can use a basis based on time:</p></div> +<div class="paragraph"><p>You can use a prerequisite based on time:</p></div> <div class="listingblock"> <div class="content"> <pre><code>$ git bundle create mybundle --since=10.days master</code></pre> @@ -1014,7 +1089,7 @@ <pre><code>$ git bundle create mybundle -10 master</code></pre> </div></div> <div class="paragraph"><p>You can run <code>git-bundle verify</code> to see if you can extract from a bundle -that was created with a basis:</p></div> +that was created with a prerequisite:</p></div> <div class="listingblock"> <div class="content"> <pre><code>$ git bundle verify mybundle</code></pre> @@ -1046,7 +1121,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2020-08-11 18:39:25 PDT + 2021-08-24 16:18:46 PDT </div> </div> </body>
diff --git a/git-bundle.txt b/git-bundle.txt index 53804ca..ac0d003 100644 --- a/git-bundle.txt +++ b/git-bundle.txt
@@ -18,21 +18,48 @@ DESCRIPTION ----------- -Some workflows require that one or more branches of development on one -machine be replicated on another machine, but the two machines cannot -be directly connected, and therefore the interactive Git protocols (git, -ssh, http) cannot be used. +Create, unpack, and manipulate "bundle" files. Bundles are used for +the "offline" transfer of Git objects without an active "server" +sitting on the other side of the network connection. -The 'git bundle' command packages objects and references in an archive -at the originating machine, which can then be imported into another -repository using 'git fetch', 'git pull', or 'git clone', -after moving the archive by some means (e.g., by sneakernet). +They can be used to create both incremental and full backups of a +repository, and to relay the state of the references in one repository +to another. -As no -direct connection between the repositories exists, the user must specify a -basis for the bundle that is held by the destination repository: the -bundle assumes that all objects in the basis are already in the -destination repository. +Git commands that fetch or otherwise "read" via protocols such as +`ssh://` and `https://` can also operate on bundle files. It is +possible linkgit:git-clone[1] a new repository from a bundle, to use +linkgit:git-fetch[1] to fetch from one, and to list the references +contained within it with linkgit:git-ls-remote[1]. There's no +corresponding "write" support, i.e.a 'git push' into a bundle is not +supported. + +See the "EXAMPLES" section below for examples of how to use bundles. + +BUNDLE FORMAT +------------- + +Bundles are `.pack` files (see linkgit:git-pack-objects[1]) with a +header indicating what references are contained within the bundle. + +Like the the packed archive format itself bundles can either be +self-contained, or be created using exclusions. +See the "OBJECT PREREQUISITES" section below. + +Bundles created using revision exclusions are "thin packs" created +using the `--thin` option to linkgit:git-pack-objects[1], and +unbundled using the `--fix-thin` option to linkgit:git-index-pack[1]. + +There is no option to create a "thick pack" when using revision +exclusions, users should not be concerned about the difference. By +using "thin packs" bundles created using exclusions are smaller in +size. That they're "thin" under the hood is merely noted here as a +curiosity, and as a reference to other documentation + +See link:technical/bundle-format.html[the `bundle-format` +documentation] for more details and the discussion of "thin pack" in +link:technical/pack-format.html[the pack format documentation] for +further details. OPTIONS ------- @@ -117,28 +144,88 @@ SPECIFYING REFERENCES --------------------- -'git bundle' will only package references that are shown by -'git show-ref': this includes heads, tags, and remote heads. References -such as `master~1` cannot be packaged, but are perfectly suitable for -defining the basis. More than one reference may be packaged, and more -than one basis can be specified. The objects packaged are those not -contained in the union of the given bases. Each basis can be -specified explicitly (e.g. `^master~10`), or implicitly (e.g. -`master~10..master`, `--since=10.days.ago master`). +Revisions must accompanied by reference names to be packaged in a +bundle. -It is very important that the basis used be held by the destination. +More than one reference may be packaged, and more than one set of prerequisite objects can +be specified. The objects packaged are those not contained in the +union of the prerequisites. + +The 'git bundle create' command resolves the reference names for you +using the same rules as `git rev-parse --abbrev-ref=loose`. Each +prerequisite can be specified explicitly (e.g. `^master~10`), or implicitly +(e.g. `master~10..master`, `--since=10.days.ago master`). + +All of these simple cases are OK (assuming we have a "master" and +"next" branch): + +---------------- +$ git bundle create master.bundle master +$ echo master | git bundle create master.bundle --stdin +$ git bundle create master-and-next.bundle master next +$ (echo master; echo next) | git bundle create master-and-next.bundle --stdin +---------------- + +And so are these (and the same but omitted `--stdin` examples): + +---------------- +$ git bundle create recent-master.bundle master~10..master +$ git bundle create recent-updates.bundle master~10..master next~5..next +---------------- + +A revision name or a range whose right-hand-side cannot be resolved to +a reference is not accepted: + +---------------- +$ git bundle create HEAD.bundle $(git rev-parse HEAD) +fatal: Refusing to create empty bundle. +$ git bundle create master-yesterday.bundle master~10..master~5 +fatal: Refusing to create empty bundle. +---------------- + +OBJECT PREREQUISITES +-------------------- + +When creating bundles it is possible to create a self-contained bundle +that can be unbundled in a repository with no common history, as well +as providing negative revisions to exclude objects needed in the +earlier parts of the history. + +Feeding a revision such as `new` to `git bundle create` will create a +bundle file that contains all the objects reachable from the revision +`new`. That bundle can be unbundled in any repository to obtain a full +history that leads to the revision `new`: + +---------------- +$ git bundle create full.bundle new +---------------- + +A revision range such as `old..new` will produce a bundle file that +will require the revision `old` (and any objects reachable from it) +to exist for the bundle to be "unbundle"-able: + +---------------- +$ git bundle create full.bundle old..new +---------------- + +A self-contained bundle without any prerequisites can be extracted +into anywhere, even into an empty repository, or be cloned from +(i.e., `new`, but not `old..new`). + It is okay to err on the side of caution, causing the bundle file to contain objects already in the destination, as these are ignored when unpacking at the destination. -`git clone` can use any bundle created without negative refspecs -(e.g., `new`, but not `old..new`). If you want to match `git clone --mirror`, which would include your refs such as `refs/remotes/*`, use `--all`. If you want to provide the same set of refs that a clone directly from the source repository would get, use `--branches --tags` for the `<git-rev-list-args>`. +The 'git bundle verify' command can be used to check whether your +recipient repository has the required prerequisite commits for a +bundle. + EXAMPLES -------- @@ -149,7 +236,7 @@ We want to update R2 with development made on the branch master in R1. To bootstrap the process, you can first create a bundle that does not have -any basis. You can use a tag to remember up to what commit you last +any prerequisites. You can use a tag to remember up to what commit you last processed, in order to make it easy to later update the other repository with an incremental bundle: @@ -200,7 +287,7 @@ If you know up to what commit the intended recipient repository should have the necessary objects, you can use that knowledge to specify the -basis, giving a cut-off point to limit the revisions and objects that go +prerequisites, giving a cut-off point to limit the revisions and objects that go in the resulting bundle. The previous example used the lastR2bundle tag for this purpose, but you can use any other options that you would give to the linkgit:git-log[1] command. Here are more examples: @@ -211,7 +298,7 @@ $ git bundle create mybundle v1.0.0..master ---------------- -You can use a basis based on time: +You can use a prerequisite based on time: ---------------- $ git bundle create mybundle --since=10.days master @@ -224,7 +311,7 @@ ---------------- You can run `git-bundle verify` to see if you can extract from a bundle -that was created with a basis: +that was created with a prerequisite: ---------------- $ git bundle verify mybundle
diff --git a/git-config.html b/git-config.html index 46df82a..f442117 100644 --- a/git-config.html +++ b/git-config.html
@@ -1839,6 +1839,14 @@ is expanded to the value of <code>$HOME</code>, and <code>~user/</code> to the specified user’s home directory. </p> +<div class="paragraph"><p>If a path starts with <code>%(prefix)/</code>, the remainder is interpreted as a +path relative to Git’s "runtime prefix", i.e. relative to the location +where Git itself was installed. For example, <code>%(prefix)/bin/</code> refers to +the directory in which the Git executable itself lives. If Git was +compiled without runtime prefix support, the compiled-in prefix will be +subsituted instead. In the unlikely event that a literal path needs to +be specified that should <em>not</em> be expanded, it needs to be prefixed by +<code>./</code>, like so: <code>./%(prefix)/bin</code>.</p></div> </dd> </dl></div> </div>
diff --git a/git-for-each-ref.html b/git-for-each-ref.html index 0dbb45f..127f20a 100644 --- a/git-for-each-ref.html +++ b/git-for-each-ref.html
@@ -1112,6 +1112,20 @@ <code>committeremail</code> and <code>taggeremail</code>), <code>:trim</code> can be appended to get the email without angle brackets, and <code>:localpart</code> to get the part before the <code>@</code> symbol out of the trimmed email.</p></div> +<div class="paragraph"><p>The raw data in an object is <code>raw</code>.</p></div> +<div class="dlist"><dl> +<dt class="hdlist1"> +raw:size +</dt> +<dd> +<p> + The raw data size of the object. +</p> +</dd> +</dl></div> +<div class="paragraph"><p>Note that <code>--format=%(raw)</code> can not be used with <code>--python</code>, <code>--shell</code>, <code>--tcl</code>, +because such language may not support arbitrary binary data in their string +variable type.</p></div> <div class="paragraph"><p>The message in a commit or a tag object is <code>contents</code>, from which <code>contents:<part></code> can be used to extract various parts out of:</p></div> <div class="dlist"><dl> @@ -1324,7 +1338,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-03-02 23:05:01 PST + 2021-08-24 16:18:46 PDT </div> </div> </body>
diff --git a/git-for-each-ref.txt b/git-for-each-ref.txt index 2ae2478..6da899c 100644 --- a/git-for-each-ref.txt +++ b/git-for-each-ref.txt
@@ -235,6 +235,15 @@ without angle brackets, and `:localpart` to get the part before the `@` symbol out of the trimmed email. +The raw data in an object is `raw`. + +raw:size:: + The raw data size of the object. + +Note that `--format=%(raw)` can not be used with `--python`, `--shell`, `--tcl`, +because such language may not support arbitrary binary data in their string +variable type. + The message in a commit or a tag object is `contents`, from which `contents:<part>` can be used to extract various parts out of:
diff --git a/howto/coordinate-embargoed-releases.html b/howto/coordinate-embargoed-releases.html index 4d93793..e60aa0f 100644 --- a/howto/coordinate-embargoed-releases.html +++ b/howto/coordinate-embargoed-releases.html
@@ -873,7 +873,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:35 PDT + 2021-08-24 16:19:43 PDT </div> </div> </body>
diff --git a/howto/keep-canonical-history-correct.html b/howto/keep-canonical-history-correct.html index 7f437a0..00bc40d 100644 --- a/howto/keep-canonical-history-correct.html +++ b/howto/keep-canonical-history-correct.html
@@ -938,7 +938,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:34 PDT + 2021-08-24 16:19:43 PDT </div> </div> </body>
diff --git a/howto/maintain-git.html b/howto/maintain-git.html index 13952df..e7f9468 100644 --- a/howto/maintain-git.html +++ b/howto/maintain-git.html
@@ -1469,7 +1469,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:35 PDT + 2021-08-24 16:19:43 PDT </div> </div> </body>
diff --git a/howto/new-command.html b/howto/new-command.html index 336c013..6edd7e0 100644 --- a/howto/new-command.html +++ b/howto/new-command.html
@@ -863,7 +863,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:28 PDT + 2021-08-24 16:19:39 PDT </div> </div> </body>
diff --git a/howto/rebase-from-internal-branch.html b/howto/rebase-from-internal-branch.html index f795daa..ff8346e 100644 --- a/howto/rebase-from-internal-branch.html +++ b/howto/rebase-from-internal-branch.html
@@ -895,7 +895,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:34 PDT + 2021-08-24 16:19:43 PDT </div> </div> </body>
diff --git a/howto/rebuild-from-update-hook.html b/howto/rebuild-from-update-hook.html index 8ea60d3..1652a0b 100644 --- a/howto/rebuild-from-update-hook.html +++ b/howto/rebuild-from-update-hook.html
@@ -847,7 +847,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:34 PDT + 2021-08-24 16:19:43 PDT </div> </div> </body>
diff --git a/howto/recover-corrupted-blob-object.html b/howto/recover-corrupted-blob-object.html index 166ffcc..6b4c5d1 100644 --- a/howto/recover-corrupted-blob-object.html +++ b/howto/recover-corrupted-blob-object.html
@@ -880,7 +880,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:33 PDT + 2021-08-24 16:19:42 PDT </div> </div> </body>
diff --git a/howto/recover-corrupted-object-harder.html b/howto/recover-corrupted-object-harder.html index a12d2d8..48e78e3 100644 --- a/howto/recover-corrupted-object-harder.html +++ b/howto/recover-corrupted-object-harder.html
@@ -1189,7 +1189,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:33 PDT + 2021-08-24 16:19:43 PDT </div> </div> </body>
diff --git a/howto/revert-a-faulty-merge.html b/howto/revert-a-faulty-merge.html index 24f934d..6db49cc 100644 --- a/howto/revert-a-faulty-merge.html +++ b/howto/revert-a-faulty-merge.html
@@ -1025,7 +1025,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:32 PDT + 2021-08-24 16:19:42 PDT </div> </div> </body>
diff --git a/howto/revert-branch-rebase.html b/howto/revert-branch-rebase.html index 2057554..a666ece 100644 --- a/howto/revert-branch-rebase.html +++ b/howto/revert-branch-rebase.html
@@ -907,7 +907,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:28 PDT + 2021-08-24 16:19:40 PDT </div> </div> </body>
diff --git a/howto/separating-topic-branches.html b/howto/separating-topic-branches.html index 77e0d8a..e01e563 100644 --- a/howto/separating-topic-branches.html +++ b/howto/separating-topic-branches.html
@@ -841,7 +841,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:32 PDT + 2021-08-24 16:19:42 PDT </div> </div> </body>
diff --git a/howto/setup-git-server-over-http.html b/howto/setup-git-server-over-http.html index 9632d64..62a0dcd 100644 --- a/howto/setup-git-server-over-http.html +++ b/howto/setup-git-server-over-http.html
@@ -1071,7 +1071,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:31 PDT + 2021-08-24 16:19:41 PDT </div> </div> </body>
diff --git a/howto/update-hook-example.html b/howto/update-hook-example.html index 66530eb..7a8c7a2 100644 --- a/howto/update-hook-example.html +++ b/howto/update-hook-example.html
@@ -930,7 +930,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:31 PDT + 2021-08-24 16:19:41 PDT </div> </div> </body>
diff --git a/howto/use-git-daemon.html b/howto/use-git-daemon.html index 39410d1..0f5234c 100644 --- a/howto/use-git-daemon.html +++ b/howto/use-git-daemon.html
@@ -791,7 +791,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:30 PDT + 2021-08-24 16:19:41 PDT </div> </div> </body>
diff --git a/howto/using-merge-subtree.html b/howto/using-merge-subtree.html index 942347e..984f60e 100644 --- a/howto/using-merge-subtree.html +++ b/howto/using-merge-subtree.html
@@ -848,7 +848,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:29 PDT + 2021-08-24 16:19:40 PDT </div> </div> </body>
diff --git a/howto/using-signed-tag-in-pull-request.html b/howto/using-signed-tag-in-pull-request.html index ff1e660..68a1d7f 100644 --- a/howto/using-signed-tag-in-pull-request.html +++ b/howto/using-signed-tag-in-pull-request.html
@@ -952,7 +952,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-08-16 14:18:29 PDT + 2021-08-24 16:19:40 PDT </div> </div> </body>
diff --git a/technical/api-trace2.html b/technical/api-trace2.html index 78f28e2..97bffdf 100644 --- a/technical/api-trace2.html +++ b/technical/api-trace2.html
@@ -1371,6 +1371,25 @@ </div></div> </dd> <dt class="hdlist1"> +<code>"cmd_ancestry"</code> +</dt> +<dd> +<p> + This event contains the text command name for the parent (and earlier + generations of parents) of the current process, in an array ordered from + nearest parent to furthest great-grandparent. It may not be implemented + on all platforms. +</p> +<div class="listingblock"> +<div class="content"> +<pre><code>{ + "event":"cmd_ancestry", + ... + "ancestry":["bash","tmux: server","systemd"] +}</code></pre> +</div></div> +</dd> +<dt class="hdlist1"> <code>"cmd_name"</code> </dt> <dd> @@ -2156,7 +2175,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2021-07-13 17:37:55 PDT + 2021-08-24 16:18:46 PDT </div> </div> </body> diff --git a/technical/api-trace2.txt b/technical/api-trace2.txt index 037a91c..b9f3198 100644 --- a/technical/api-trace2.txt +++ b/technical/api-trace2.txt
@@ -493,6 +493,20 @@ } ------------ +`"cmd_ancestry"`:: + This event contains the text command name for the parent (and earlier + generations of parents) of the current process, in an array ordered from + nearest parent to furthest great-grandparent. It may not be implemented + on all platforms. ++ +------------ +{ + "event":"cmd_ancestry", + ... + "ancestry":["bash","tmux: server","systemd"] +} +------------ + `"cmd_name"`:: This event contains the command name for this git process and the hierarchy of commands from parent git processes. 